Skip to content

Release: v2.1.0 - #792

Open
kalenkevich wants to merge 1 commit into
mainfrom
release-please--branches--main
Open

Release: v2.1.0#792
kalenkevich wants to merge 1 commit into
mainfrom
release-please--branches--main

Conversation

@kalenkevich

@kalenkevich kalenkevich commented Aug 21, 2026

Copy link
Copy Markdown
Collaborator

Automated Release PR

adk: 2.1.0

2.1.0 (2026-09-04)

Features

  • plugins: add ReflectAndRetryToolPlugin and ReflectAndRetryModelPlugin for self-healing error recovery (#631) (1b6ea6d)
  • Port the typed-errors module (errors/) from adk-python (#583) (fab19d0)

Bug Fixes

  • a2a: propagate request metadata to agent execution (#752) (#768) (bb2dd8f)
  • agents: carry request-input resume inputs in their own type (#822) (8664b6e)
  • auth: redact OAuth2 authorization code from malformed-callback-URI log (#640) (08f4f24)
  • auth: reject an empty credentialKey before storing the credential (#818) (8f792bb)
  • build: make the web build loadable outside Node (#837) (5b9c306)
  • close two remaining author-blind confirmation-resolution paths (#755) (f9d6d91)
  • core: gracefully handle unregistered tool calls (#790) (6be4195)
  • core: load artifacts and MCP resources when other tools are call… (#639) (b723201)
  • core: make built-in tools resolvable by name (#811) (e7fab37)
  • core: stop a surviving grandchild from hanging code execution (#793) (173462a), closes #622
  • core: type the live session mock in gemini_llm_connection_test (#849) (bfe904e)
  • drop the redundant ExtendedInteractionSSEEvent self-cast in the streaming loop (#827) (e9f187f)
  • preserve EventActions when a long-running tool returns no response (#571) (c6ad9c2)
  • scrub credential material before forwarding to a remote A2A peer (#767) (f3c27fd)
  • sessions: import Client from the @google-cloud/vertexai package root (#801) (3aaf49b)
  • tools: drop no-unused-vars suppressions in BaseToolset.processLlmRequest (#851) (1a699f4)
  • type the load_mcp_resource LlmRequest fixtures instead of double-casting (#836) (071f795)
devtools: 2.1.0

2.1.0 (2026-09-04)

Bug Fixes

Dependencies

  • The following workspace dependencies were updated
    • dependencies
      • @google/adk bumped from ^2.0.0 to ^2.1.0
integrations: 2.1.0

2.1.0 (2026-09-04)

Miscellaneous Chores

  • integrations: Synchronize adk versions

Dependencies

  • The following workspace dependencies were updated
    • dependencies
      • @google/adk bumped from ^2.0.0 to ^2.1.0
main: 2.1.0

2.1.0 (2026-09-04)

Features

  • plugins: add ReflectAndRetryToolPlugin and ReflectAndRetryModelPlugin for self-healing error recovery (#631) (1b6ea6d)
  • Port the typed-errors module (errors/) from adk-python (#583) (fab19d0)

Bug Fixes

  • a2a: propagate request metadata to agent execution (#752) (#768) (bb2dd8f)
  • agents: carry request-input resume inputs in their own type (#822) (8664b6e)
  • auth: redact OAuth2 authorization code from malformed-callback-URI log (#640) (08f4f24)
  • auth: reject an empty credentialKey before storing the credential (#818) (8f792bb)
  • bind one appName in the Vertex AI compaction e2e test (#848) (675c2f3)
  • build: make the web build loadable outside Node (#837) (5b9c306)
  • close two remaining author-blind confirmation-resolution paths (#755) (f9d6d91)
  • core: gracefully handle unregistered tool calls (#790) (6be4195)
  • core: load artifacts and MCP resources when other tools are call… (#639) (b723201)
  • core: make built-in tools resolvable by name (#811) (e7fab37)
  • core: stop a surviving grandchild from hanging code execution (#793) (173462a), closes #622
  • core: type the live session mock in gemini_llm_connection_test (#849) (bfe904e)
  • dev: let --bundle false actually load an agent (#791) (91357fd), closes #714
  • drop the redundant ExtendedInteractionSSEEvent self-cast in the streaming loop (#827) (e9f187f)
  • guard reads in the dev server against DNS rebinding (#744) (0fe9581)
  • preserve EventActions when a long-running tool returns no response (#571) (c6ad9c2)
  • remove the no-op @ts-ignore on the esbuild-shim-plugin import (#805) (9566743)
  • scrub credential material before forwarding to a remote A2A peer (#767) (f3c27fd)
  • sessions: import Client from the @google-cloud/vertexai package root (#801) (3aaf49b)
  • test: import Client from the @google-cloud/vertexai package root (#825) (321a2bc)
  • tests: delete the unreachable duplicate generateContentAsync from the js fixtures (#850) (2dc5c4a)
  • tests: read the compaction Vertex e2e region from GOOGLE_CLOUD_LOCATION (#835) (daad4db)
  • tools: drop no-unused-vars suppressions in BaseToolset.processLlmRequest (#851) (1a699f4)
  • type the load_mcp_resource LlmRequest fixtures instead of double-casting (#836) (071f795)

This PR was generated with Release Please. See documentation.

@AmaadMartin AmaadMartin left a comment

Copy link
Copy Markdown
Collaborator

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

Approve. Release Please bump 2.0.0 -> 2.0.1. The only fix commit since adk-v2.0.0 is fix(dev) #791, and it appears in the dev changelog; chore #786 is correctly excluded by the node changelog sections. The linked-versions plugin bumps all four components together, so the manifest, three version.ts files, the package.json files, and the lockfile are consistent. Required checks and run-tests all pass at review time.

@kalenkevich
kalenkevich force-pushed the release-please--branches--main branch from 6bc6ac8 to 166bbc6 Compare August 22, 2026 02:49

@AmaadMartin AmaadMartin left a comment

Copy link
Copy Markdown
Collaborator

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

Approve. Release Please bump 2.0.0 -> 2.0.1, re-verified at head 166bbc6. The changelog matches the commit range adk-v2.0.0..main exactly: fix(core) #793 and fix(dev) #791 both appear; chore #786 is correctly excluded. Version 2.0.1 is consistent across the manifest, three version.ts files, package.json files, and the lockfile. Required checks pass; run-tests was still running at review time.

@kalenkevich
kalenkevich force-pushed the release-please--branches--main branch 2 times, most recently from de3fca3 to 7900c3e Compare August 22, 2026 04:23

@AmaadMartin AmaadMartin left a comment

Copy link
Copy Markdown
Collaborator

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

Approve. Each fix: commit since v2.0.0 (#768, #639, #793, #791) appears in the correct package changelog, and the two other commits (#786 chore, #794 test) are correctly hidden by the default config; no commit uses a misplaced bang, so none was dropped. The fix-only set gives a correct patch bump, and all four packages plus the lockfile move 2.0.0 to 2.0.1 consistently. CI: run-tests (windows-latest) failed on a known flake in unsafe_local_code_executor_test.ts (5000ms timeout, #622), a file this PR does not touch; the required checks (cla/google, check-license, scan-pr) all pass.

@AmaadMartin AmaadMartin left a comment

Copy link
Copy Markdown
Collaborator

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

Approved. This is a standard Release Please release PR for v2.0.1. The diff changes only release files: the manifest, the three changelogs, the package versions, and the lockfile. I verified that all four fix commits since v2.0.0 (#768, #639, #793, #791) appear in a changelog, and that the 2.0.0 to 2.0.1 bump is consistent across every file. CI note: run-tests (windows-latest) failed on unsafe_local_code_executor_test.ts timeouts, a known flake in a file this PR does not touch; macOS and Ubuntu passed.

@kalenkevich
kalenkevich force-pushed the release-please--branches--main branch from 7900c3e to 1dc6b79 Compare August 24, 2026 21:46
@kalenkevich kalenkevich changed the title Release: v2.0.1 Release: v2.1.0 Aug 24, 2026
@kalenkevich
kalenkevich force-pushed the release-please--branches--main branch 2 times, most recently from af24ae8 to 437a325 Compare August 24, 2026 21:55

@AmaadMartin AmaadMartin left a comment

Copy link
Copy Markdown
Collaborator

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

Approve. Standard Release Please bump to v2.1.0. I checked the changelog against the commit range adk-v2.0.0..HEAD: every feat/fix commit is listed, and the chore (#786) and test (#794) commits are correctly excluded. The minor bump is right — #631 is the only feat and no commit is breaking. Version strings match across the manifest, all package.json, all version.ts, and package-lock.json. CI was green at review time.

@AmaadMartin AmaadMartin left a comment

Copy link
Copy Markdown
Collaborator

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

Approve. Standard Release Please bump to v2.1.0. Every feat/fix commit merged since adk-v2.0.0 appears in a changelog: #631, #640, #571, #768, #639, #793 in core and #791 in dev. The two omitted commits are a chore (#786) and a test (#794), which Release Please excludes correctly. The diff only touches release files (manifest, changelogs, version.ts, package.json, lockfile version fields) with no registry URL churn. All required checks and run-tests passed at review time.

@AmaadMartin AmaadMartin left a comment

Copy link
Copy Markdown
Collaborator

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

Approve. This is a standard Release Please PR: version bumps 2.0.0 -> 2.1.0 and changelog entries only, no source logic.

I checked the changelog against the commit range main-v2.0.0...main. All nine commits map correctly: one feat and five fixes go to the core changelog, one fix goes to the dev changelog, and the chore and test commits are correctly omitted. No commit is dropped, and no commit carries a breaking-change marker, so the minor bump is right. The file set matches every prior release PR.

CI was fully green at review time.

@kalenkevich
kalenkevich force-pushed the release-please--branches--main branch from 437a325 to 8cef16c Compare August 25, 2026 02:14

@AmaadMartin AmaadMartin left a comment

Copy link
Copy Markdown
Collaborator

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

Approve. This is a mechanical Release Please diff: version bumps, changelog entries, and lockfile version strings only, with no source, dependency, or workflow change. The changelog matches the commit range main-v2.0.0...main: all eight feat/fix commits appear (seven in core, #791 in dev), and the chore (#786) and test (#794) commits are correctly excluded. No breaking-change commit was dropped, so the 2.0.0 to 2.1.0 minor bump is correct. CI is green at review time.

@kalenkevich
kalenkevich force-pushed the release-please--branches--main branch 2 times, most recently from 717c891 to 9c3022c Compare August 25, 2026 17:10

@AmaadMartin AmaadMartin left a comment

Copy link
Copy Markdown
Collaborator

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

Approve. This is a standard Release Please PR for v2.1.0.

I verified the changelog against the commit range main-v2.0.0...HEAD. Every feat/fix commit maps to an entry: 8 core fixes plus 1 feature (#631), and 2 dev fixes (#791, #744). The chore (#786) and test (#794) commits are correctly excluded. The minor bump is correct because a feat landed and no commit has a breaking-change marker. Version bumps are consistent across the manifest, package.json, version.ts, and the lockfile, and the lockfile churn is version strings only. CI was fully green at review time.

@AmaadMartin AmaadMartin left a comment

Copy link
Copy Markdown
Collaborator

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

Approve. This is a Release Please diff: version bumps to 2.1.0, changelog entries, and matching lockfile changes. I checked the changelog against the commit range main-v2.0.0..main: every feat and fix commit appears, and the only omitted commits are #786 (chore) and #794 (test), which release-please hides by default. Versions are consistent across the manifest, package.json, version.ts, and lockfile, and no source code changed. CI was green at review time, including run-tests on all three platforms.

@kalenkevich
kalenkevich force-pushed the release-please--branches--main branch from 9c3022c to 8775a4d Compare August 25, 2026 18:12

@AmaadMartin AmaadMartin left a comment

Copy link
Copy Markdown
Collaborator

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

Approve. Standard Release Please diff at head 8775a4d: version bumps 2.0.0 -> 2.1.0, changelog entries, and lockfile version strings. No source logic changes.

I audited the changelog against the commit range adk-v2.0.0..head. All 12 conventional commits appear (10 core, 2 dev); the chore (#786) and test (#794) are correctly excluded. No misplaced ! bang drops a commit. The minor bump matches the one feat (#631).

CI: run-tests passed on ubuntu and macOS; windows was still running at review time. scan-pr, check-license, cla/google, check-changes all pass.

@kalenkevich
kalenkevich force-pushed the release-please--branches--main branch from 8775a4d to 491bdae Compare August 26, 2026 20:27

@AmaadMartin AmaadMartin left a comment

Copy link
Copy Markdown
Collaborator

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

Approve. Automated Release Please PR for v2.1.0. I checked the three changelogs against the commit range adk-v2.0.0..HEAD: all 13 release commits (12 fix, 1 feat) are listed, and the excluded chore/test/docs commits are correctly dropped. The minor bump matches feat(plugins) #631, no breaking-change bang was lost, and all four components link to 2.1.0 across the manifest, package.json, version.ts, and the lockfile. CI: run-tests passed on ubuntu and the rest were still running at review time; CI does not gate this decision.

@kalenkevich
kalenkevich force-pushed the release-please--branches--main branch from 491bdae to 9004a55 Compare August 27, 2026 19:16

@AmaadMartin AmaadMartin left a comment

Copy link
Copy Markdown
Collaborator

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

Approve. This is a release-please PR for v2.1.0. I checked the changelog against the commit range adk-v2.0.0..HEAD: all 15 feat/fix commits are listed, and the three omitted PRs (#786 chore, #794 test, #800 docs) are correctly excluded. The version bump to 2.1.0 is consistent across the manifest, every package.json, the version.ts files, and package-lock.json. The three required checks pass; the run-tests matrix was still running at review time.

@kalenkevich
kalenkevich force-pushed the release-please--branches--main branch from 9004a55 to 0f15060 Compare August 27, 2026 22:17

@AmaadMartin AmaadMartin left a comment

Copy link
Copy Markdown
Collaborator

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

Verified the generated release against the commit range adk-v2.0.0...HEAD. Every feat/fix commit that touches a package appears in the correct changelog, and the version bump is consistent (2.0.0 to 2.1.0) across the manifest, package.json files, version.ts files, and the lockfile. The omitted commits are all chore/test/docs (excluded by default) or fix(test) #825, which touches only root tests/integration/** and routes to the skip-changelog main component. No misplaced breaking-change marker drops a commit. CI: required checks pass; the run-tests OS matrix was still running at review time.

@kalenkevich
kalenkevich force-pushed the release-please--branches--main branch from 0f15060 to 41e4686 Compare August 28, 2026 22:17

@AmaadMartin AmaadMartin left a comment

Copy link
Copy Markdown
Collaborator

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

Approve. Standard Release Please diff at head 41e4686: version bumps 2.0.0 -> 2.1.0 and generated changelog entries only, no source code. I checked each component changelog against commits adk-v2.0.0...HEAD; every user-facing feat/fix is present. #825 (fix(test)) touches only root tests/integration/ files, so it maps to the root component with no CHANGELOG file, not a dropped fix. run-tests was still pending at review time; required checks pass.

@kalenkevich
kalenkevich force-pushed the release-please--branches--main branch from 41e4686 to bb9cb42 Compare August 31, 2026 02:44

@AmaadMartin AmaadMartin left a comment

Copy link
Copy Markdown
Collaborator

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

Approve. This is a release-please PR bumping 2.0.0 -> 2.1.0. The minor bump is correct: two feat commits (#631, #583) and no breaking change. I checked every changelog entry against the adk-v2.0.0...main commit range; every feat and fix that touches a package appears in the right CHANGELOG, and #825 (fix(test), only tests/integration/) maps to the skip-changelog main component, so its absence is correct. Versions are consistent across the manifest, all package.json, version.ts, and the lockfile, and the diff touches only release-please-owned files. CI was green on all three run-tests OSes at review time.

@kalenkevich
kalenkevich force-pushed the release-please--branches--main branch from bb9cb42 to f91b6a9 Compare September 2, 2026 21:51

@AmaadMartin AmaadMartin left a comment

Copy link
Copy Markdown
Collaborator

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

Approve. This is a Release Please generated PR for v2.1.0. I checked the changelog against the commit range adk-v2.0.0...main: every feat and fix commit is present and correctly attributed, and #825 (fix(test)) maps to the root component, which sets skip-changelog, so it correctly appears only in the PR body. No commit carries a breaking-change marker, so the 2.0.0 to 2.1.0 minor bump is right, and the version files and lockfile all match. CI: the required checks (cla/google, check-license, scan-pr) pass; run-tests fails only on windows-latest at unsafe_local_code_executor_test.ts, a known 5000ms timeout flake in a file this PR does not touch.

@kalenkevich
kalenkevich force-pushed the release-please--branches--main branch from f91b6a9 to 216432f Compare September 3, 2026 20:35

@AmaadMartin AmaadMartin left a comment

Copy link
Copy Markdown
Collaborator

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

Approve. This is an automated Release Please PR. It bumps 2.0.0 to 2.1.0 across the manifest, the package.json files, the version.ts files, and the lockfile.

I checked the changelog against the commit range adk-v2.0.0...HEAD. Every feat and fix commit that touches a package appears in the correct changelog. The chore, test, and docs commits are correctly hidden, and fix(test) #825 is correctly skipped because it touches only root tests/ files, which map to the skip-changelog root component.

No breaking-change footer exists in the range, so the minor bump is correct. All CI checks pass at review time. The PR body carries no instructions to a reviewer.

@kalenkevich
kalenkevich force-pushed the release-please--branches--main branch 2 times, most recently from 16badfe to 4031330 Compare September 3, 2026 21:18

@AmaadMartin AmaadMartin left a comment

Copy link
Copy Markdown
Collaborator

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

Clean automated release PR (2.0.0 -> 2.1.0). I verified the changelog against the commit range adk-v2.0.0..main: every feat and fix that touches a package path is listed. fix(test) #825 is correctly absent because it only changes root tests/integration files, outside the core, dev, and integrations paths. The range has no breaking change, so the minor bump is correct. The diff is only generated release files and version-string lockfile churn. Required checks pass; the run-tests matrix was still running at review time.

@kalenkevich
kalenkevich force-pushed the release-please--branches--main branch 2 times, most recently from 8d7fe81 to 0a5ea0b Compare September 4, 2026 21:52
@kalenkevich
kalenkevich force-pushed the release-please--branches--main branch from 0a5ea0b to e39ec43 Compare September 4, 2026 22:03

@AmaadMartin AmaadMartin left a comment

Copy link
Copy Markdown
Collaborator

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

Approve. This is a machine-generated release-please PR. It bumps all packages 2.0.0 to 2.1.0 and updates the changelogs, manifest, and lockfile. I checked every feat and fix commit since adk-v2.0.0 against the changelog: all user-facing changes are listed, and the only omissions are four test-only commits (#825, #835, #848, #850) that release-please hides by default. Versions are consistent everywhere and the required CI checks pass at this head.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Projects

None yet

3 participants